Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

docs($animate): document the 3rd party framework compatibility issues #ngEurope #9722

Closed
wants to merge 1 commit into from

Conversation

mgcrea
Copy link
Contributor

@mgcrea mgcrea commented Oct 21, 2014

Fixes #8569, I hope the wording is both correct and clear enough.

@@ -219,6 +219,12 @@
* Also, try not to mix the two class-based animation flavors together since the CSS code may become
* overly complex.
*
* <div class="alert alert-warning">
* **Note:** Some third-party frameworks place animation duration defaults across many element or className selectors in order to make their code small and reuseable.
* This can lead to issues with ngAnimate, which is expecting actual animations on theses elements and has to wait for their completion.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which is expecting actual animations on these elements

@mgcrea
Copy link
Contributor Author

mgcrea commented Oct 21, 2014

@rodyhaddad fixed the typo, thanks.

@rodyhaddad
Copy link
Contributor

Can you add an example about how you'd do this in css? (or the side-effects of this on your css)
Reading the thing about the animate- prefix doesn't make it clear.

@petebacondarwin
Copy link
Contributor

I merged this with a few changes. Code blocks in div blocks don't format very well. So I moved it into a section of its own.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Documentation page for using ngAnimate with 3rd party frameworks
5 participants